home *** CD-ROM | disk | FTP | other *** search
- Path: inforamp.net!ts26-11
- From: rmorin@inforamp.net (Randy Charles Morin)
- Newsgroups: comp.lang.c++
- Subject: Re: What is a test harness?
- Date: Wed, 06 Mar 96 07:34:00 GMT
- Organization: MiddleWorld SoftWare
- Message-ID: <4hjf4v$elu@sam.inforamp.net>
- References: <313C00F0.51B5@bhp.com.au>
- NNTP-Posting-Host: ts26-11.tor.inforamp.net
- X-Newsreader: News Xpress Version 1.0 Beta #4
-
- In article <313C00F0.51B5@bhp.com.au>, bowen.richard.rw@bhp.com.au wrote:
- >What is a test harness and how can you use it to test a class?
-
- Especially in big projects, some classes are developed before the classes that
- use them are developed. On one project last fall, I was responsible for
- writing 20 dialogs, another person wrote 20 dialog and yet another person
- wrote the main window. Since the main application was not ready, I could not
- link my dialogs to anything to test them. Therefor, I created a small
- test front-end. The test front-end was a screen with a button to execute the
- dialog and a few controls to input the parameters that are passes to the
- dialog. When the dialog terminated the output was displayed in test
- front-end. Thus, I was able to fully test the dialog without actually linking
- it to the application. This test front-end is called a harness. Basically a
- program that allows you to test components (and classes) of an application
- without linking the components to the application.
-
- Tell me if you don't understand my explanation. I tried not to act like a
- dictionary.
-
- Agrivar
-